Apparatus and method for management of electronic notices

ABSTRACT

In certain embodiments, an apparatus includes a memory and a processor. The processor is operable to present, in a first region of a display, information associated with a first service based at least in part upon the user. The processor is further operable to present information associated with a second, third and fourth service. Additionally, the processor may receive an update to the information associated with the first service and present, in the first region of the display, the update to the information associated with the first service. Finally, the processor is operable to detect a first touch on the first region of the display indicating a selection of the first service and present details associated with the first service in response to detecting the first touch.

TECHNICAL FIELD OF THE INVENTION

This disclosure relates generally to an apparatus for the management ofelectronic notices.

BACKGROUND OF THE INVENTION

As the use of mobile devices grows, so has the desire for customers tohave real-time access to up-to-date financial information on theirmobile device. Financial institutions may offer a variety of services toa customer and may desire to present information about the services toits customers.

SUMMARY OF THE INVENTION

According to embodiments of the present disclosure, disadvantages andproblems associated with previous systems may be reduced or eliminated.

In certain embodiments, an apparatus includes a memory operable to storeuser preferences associated with a user and a processor communicativelycoupled to the memory. The processor is operable to present, in a firstregion of a display, information associated with a first service basedat least in part upon the user preferences and present, in a secondregion of the display, information associated with a second servicebased at least in part upon the user preferences. The processor isfurther operable to present, in a third region of the display,information associated with a third service based at least in part uponthe user preferences and present, in a fourth region of the display,information associated with a fourth service based at least in part uponthe user preferences. Additionally, the processor may receive an updateto the information associated with the first service and present, in thefirst region of the display, the update to the information associatedwith the first service. Finally, the processor is operable to detect afirst touch on the first region of the display indicating a selection ofthe first service and present, in at least the first, second, third, andfourth regions of the display, details associated with the first servicein response to detecting the first touch.

In some embodiments, an apparatus includes a memory operable to storeinformation associated with a plurality of transactions associated witha user and a processor communicatively coupled to the memory. Theprocessor is operable to present, in a first region of a display,information associated with a first transaction of the plurality oftransactions and present, in a second region of the display, a firstoption, the first option indicating that, when selected, the user hasmarked the first transaction for further review. The processor isfurther operable to present, in a third region of the display, a secondoption, the second option indicating that, when selected, the user hasreviewed the first transaction and present, in a fourth region of thedisplay, a notification, the notification indicating a secondtransaction of the plurality of transactions, wherein the secondtransaction occurred subsequent to the first transaction. Additionally,the processor is operable to detect a first touch on the displayindicating the selection of the second transaction and present, in thefirst region of the display, information associated with the secondtransaction in response to detecting the first touch.

According to some embodiments an apparatus includes a memory operable tostore information associated with a first plurality of events and storeinformation associated with a second plurality of events. The apparatusalso includes a processor communicatively coupled to the memory andoperable to detect a first authentication of a user, detect the firstplurality of events, wherein the first plurality of events occurredsubsequent to the first authentication of the user, and detect a secondauthentication of the user. The processor is also operable to present,in a first region of a display, information associated with a first atleast one of the first plurality of events in response to the secondauthentication of the user and present, in a second region of thedisplay, the information associated with the second plurality of events.The processor can detect a first touch on the first region of thedisplay indicating a request to present a second at least one of thefirst plurality of events and scroll the first region of the display atleast in response to the first touch. The processor is further operableto determine that each one of the first plurality of events has beenpresented and scroll the first region of the display in conjunction withthe second region of the display at least in response to determiningthat each one of the first plurality of events has been presented.

Particular embodiments of the present disclosure may provide one or moretechnical advantages. For example, in some embodiments, the system ofthe present disclosure may reduce the load on network by consolidatingnotices and transactions and related management functions. Furthermore,the system of the present disclosure, by executing an application on amobile device, may reduce the amount of processing power needed toperform various functions related to the management and retrieval ofelectronic notices.

Certain embodiments of the present disclosure may include some, all, ornone of the above advantages. One or more other technical advantages maybe readily apparent to those skilled in the art from the figures,descriptions, and claims included herein.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsfeatures and advantages, reference is now made to the followingdescription, taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 illustrates a system for providing financial information to acustomer;

FIG. 2 illustrates an example embodiment of a mobile device used in FIG.1;

FIG. 3 illustrates an example embodiment of a mobile device used in FIG.1;

FIG. 4 illustrates an example embodiment of a mobile device used in FIG.1;

FIG. 5 is a flowchart illustrating a method for managing electronicnotices;

FIG. 6 is a flowchart illustrating a method for managing electronictransactions; and

FIG. 7 is a flowchart illustrating a method for presenting electronicnotices.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates a system 100 for providing financial information to acustomer. In certain embodiments, system 100 may facilitate performanceof various functions related managing and presenting financialinformation related to various services. As particular examples, system100 may facilitate (1) the management of electronic notices, (2) themanagement of electronic transactions, and/or (3) the presentation ofelectronic notices and transactions. As provided by FIG. 1, system 100includes a device 114, network 120, and server 110. Device 114 may becommunicatively coupled to server 110 through network 120.

Generally, a user 112 may use device 114 to receive and manageinformation associated with accounts 140, transactions 150, financialservices 160 and/or events 170. Device 114 provides an interface throughwhich user 112 can receive various information associated with accounts140, transactions 150, financial services 160 and/or events 170. Throughthe interface, the user may set user preferences 165 for receivingvarious information. Using the interface, the user may also act uponinformation displayed on device 114. The user 112 can act upon theinformation by touching or swiping a touchscreen of device 114.

Financial services 160 may be any service offered by a particularfinancial institution. For example, financial services 160 may berelated to credit cards, debit cards, balance transfers, billmanagement, receipt management, savings accounts, checking accounts,investment accounts, financial budgeting, and/or any other financialservice suitable for a particular purpose. Device 114 is capable ofdisplaying information associated with any particular financial service160. User 112 can then use device 114 to act upon the informationassociated with a particular financial service 160 by using theinterface of device 114.

Events 170 may be any occurrence associated with the financialinstitution and/or user 112 that user 112 may desire to be notified. Forexample, events 170 may be the execution of a particular transaction 150or communication from the financial institution. Examples oftransactions 150 may be a purchase, a credit, a debit, a balancetransfer, a payment due, a rejected payment, a financial fee, and/or anyother financial transaction suitable for a particular purpose. Device114 is capable of displaying information associated with any particularevent 170. User 112 can then use device 114 to act upon the informationassociated with a particular event 170 by using the interface of device114.

In particular embodiments, server 110 may be configured to storeaccounts 140 and corresponding transactions 150. Server 110 may includea processor 132 and a memory 134. The functions of server 110 describedherein may be performed by processor 132 and/or memory 134.

Memory 134 may be configured to store accounts 140, correspondingtransactions 150, financial service 160, events 170, and userpreferences 165. Memory 134 may store, either permanently ortemporarily, data, operational software, or other information forprocessor 132. Memory 134 may include any one or a combination ofvolatile or non-volatile local or remote devices suitable for storinginformation. For example, memory 134 may include random access memory(RAM), read only memory (ROM), magnetic storage devices, optical storagedevices, or any other suitable information storage device or acombination of these devices.

Processor 132 may be configured to handle messages 180 associated withaccounts 140, transactions 150, financial services 160, and/or events170. In particular embodiments, processor 132 may be configured to sendand receive messages 180 to and from device 114. Messages 180 mayrequest and/or send information about accounts 140, transactions 150,financial services 160, and/or events 170. For example, message 180 maybe communicated by server 110 to device 114 and may include informationabout a new transaction 150 for a particular account 140 associated withuser 112. As another example, message 180 may be communicated by device114 to server 110 and may include information pertaining to actionstaken by user 112 with regard to a particular account 140, transaction150, financial service 160, and/or event 170.

Processor 132 may control the operation and administration of server 110by processing information received from network 120 and memory 134.Processor 132 may include any hardware and/or software that operate tocontrol and process information. Processor 132 may be a programmablelogic device, a microcontroller, a microprocessor, any suitableprocessing device, or any suitable combination of the preceding.

System 100 may include network 120. Device 114 may communicate withserver 110 through network 120. This disclosure contemplates anysuitable network 120 operable to facilitate communication between thecomponents of system 100. Network 120 may include any interconnectingsystem capable of transmitting audio, video, signals, data, messages, orany combination of the preceding. Network 120 may include all or aportion of a public switched telephone network (PSTN), a public orprivate data network, a local area network (LAN), a metropolitan areanetwork (MAN), a wide area network (WAN), a local, regional, or globalcommunication or computer network, such as the Internet, a wireline orwireless network, an enterprise intranet, or any other suitablecommunication link, including combinations thereof, operable tofacilitate communication between the components.

System 100 may include device 114. Device 114 may be communicativelycoupled to server 110 through network 120. In particular embodiments,device 114 may present a variety of information to user 112 regardingaccounts 140, transactions 150, financial services 160, and/or events170. Device 114 may also provide user 112 an interface through whichuser 112 may interact with information regarding accounts 140,transactions 150, financial services 160, and/or events 170. Forexample, device 114 may receive message 180 from server 110 providinginformation about transaction 150 which device 114 may then present, viaa display, to user 112. As another example, user 112 may be presentedwith information regarding transaction 150 and may use an interface ofdevice 114 to act upon the information regarding transaction 150. Device114 may communicate the action of user 112 to server 110 via message180.

In particular embodiments, device 114 may include a processor and memoryakin to the processor 132 and memory 134 of server 110. The memory ofdevice 114 may be configured to store accounts 140, correspondingtransactions 150, financial service 160, events 170, and userpreferences 165 of user 112. The processor of device 114 may beconfigured to control a display of device 114. In particularembodiments, the processor of device 114 may present on the display aninterface through which user 112 can efficiently manage user preferences165 for displaying and interacting with information displayed by device114. Using the interface of device 114, user 112 may also act upon theinformation displayed by device 114. The processor of device 114 mayfurther generate and communicate messages 180 with server 110. The itemsstored in the memories of device 114 and server 110 may be stored solelyin device 114, solely in server 110, or any combination thereof.

In particular embodiments, device 114 may be a mobile device 114. Device114 may be associated with user 112. For example, user 112 may be theowner of device 114. Device 114 may execute an application 190. Theapplication 190 may provide user 112 an interface through which user 112can efficiently manage user preferences 165 for displaying andinteracting with information displayed by device 114. Application 190may include logic to handle actions performed by user 112, using theinterface of device 114, upon the information displayed by device 114.Application 190, when executed, may cause device 114 to perform thefunctions described herein. Device 114 may include a processor 132 andmemory 134. Memory 134 may store the instructions or software for theapplication 190 and processor 132 may execute the instructions.

Device 114 may be a personal computer, a workstation, a laptop, awireless or cellular telephone, an electronic notebook, a personaldigital assistant, a tablet, or any other device (wireless, wireline, orotherwise) capable of receiving, processing, storing, and/orcommunicating information with other components of system 100. Device114 may also include a user interface, such as a display, a touchscreen,a microphone, keypad, or other appropriate terminal equipment usable byuser 112.

FIG. 2 illustrates an example embodiment of device 114 used in FIG. 1.As provided by FIG. 2, device 114 may be mobile device 114 that includesdisplay 200. Display 200 may include a touchscreen. User 112 mayindicate selections by touching particular regions of display 200. Forexample, display 200 may present a button and user 112 may indicate aselection or push of the button by touching the region of the display200 that presents the button. In particular embodiments, display 200 maypresent items in first region 210, second region 220, third region 230,fourth region 240, and/or fifth region 250. Items displayed in theregions may present information regarding particular accounts 140,transactions 150, financial services 160, and/or events 170. In theillustrated example, first region 210 provides information related tothe financial service 160 of bill management. Second region 220 providesinformation related to the financial service 160 of overall wealthmanagement. Third region 230 provides information related to thefinancial service 160 of receipt management (e.g., receipts associatedwith transactions 150). Fourth region 240 provides information relatedto the financial service 160 of investment management. Fifth region 250may provide details to user 112 regarding the current functionalitybeing provided by device 114.

This disclosure contemplates any region displaying information relatedto any suitable financial service 160. The regions of display 200 mayalso display updates to information in the regions in real-time. Forexample, if there is an update to the information in region 210, thenuser 112 may be notified of the update via an audio and/or visual cuefrom device 114. User 112 may touch these regions of display 200 toindicate different selections. Touching a particular region may expandto provide further information related to the particular financialservice 160. In certain embodiments, after selection of a particularregion, information related to the particular financial service 160 mayoccupy the portion of display 200 displaying first region 210, secondregion 220, third region 230, and/or fourth region 240. Display 200 mayalso include expansion bar 260. When user 112 selects expansion bar 260(e.g., using a downward swiping motion), display 200 may display aconsolidated list of all information related to the financial services160 presented in the first, second, third, and fourth regions. Thisdisclosure contemplates any suitable number and arrangement of regionsin which different components may be implemented.

FIG. 3 illustrates an example embodiment of device 114 used in FIG. 1.As provided by FIG. 3, device 114 may be mobile device 114 that includesdisplay 200. Display 200 may include a touchscreen. In particularembodiments, display 200 may present items in first region 310, secondregion 330, third region 330, and/or fourth regions 360. First region310 may present information regarding accounts 140, transactions 150,financial services 160, and/or events 170. For example, first region 310may include timestamp 312, source 314, amount 316, and type 318.Timestamp 312 may be in any date/time format that represents a specifictime a particular transaction 150 or event 170 may have occurred. Source314 may be any source for a particular transaction 150 or event 170(e.g., a vendor, a retailer, a financial institution). Amount 316 mayprovide details related to the amount of money that may be associatedwith a particular transaction 150 or event 170. Type 318 may be a typeof a particular transaction 150 or event 170 (e.g., transactions 150 orevents 170 related to credit cards, debit cards, balance transfers, billmanagement, receipt management, savings accounts, checking accounts,investment accounts, financial budgeting). Display 200 may also havesecond region 320 that presents user 112 with the option to mark aparticular transaction 150 or event 170 for further review. In certainembodiments, second region 320 may be pre-selected indicating that user112 should review the particular transaction 150 or event 170. Display200 may have third region 330, which when selected, may indicate thatuser 112 has reviewed the particular transaction 150 or event 170.

Display 200 may have fourth regions 360, which may represent one or moreother transactions 150 or events 170, if any. Fourth regions 360 mayindicate to user 112 that there are other transactions 150 or events 170for user 112 to review. In certain embodiments, transactions 150 orevents 170 in fourth regions 360 may have occurred subsequent to theparticular transaction 150 or event 170 presented in first region 310.Display 200 may also include fifth region 340 which may allow user 112to drag certain items to in order to indicate that a next item should bedisplayed. For example, user 112 may swipe from approximately firstregion 310 to fifth region 340 indicating that the item in first region310 has been reviewed. Display 200 may then display information relatedto the next transaction 150 or event 170 (e.g., represented by fourthregion 360 a).

User 112 may touch these regions of display 200 to indicate differentselections. Certain selections may provide visual or audio feedback touser 112 indicating the selection, such as playing a sound and/orchanging the state of a graphical icon. In certain embodiments, aselection may initiate communication with server 110. For example, user112 may select second region 320. In response, device 114 may generatemessage 180 to server 110 indicating that user 112 has selected aparticular transaction 150 or event 170 for further review. In someembodiments, message 180 may notify a financial institution that theselection of second region 320 indicates that user 112 is disputing theaccuracy of a certain transaction 150 or event 170. This disclosurecontemplates any suitable number and arrangement of regions in whichdifferent components may be implemented.

FIG. 4 illustrates an example embodiment of device 114 used in FIG. 1.As provided by FIG. 4, device 114 may be mobile device 114 that includesdisplay 200. Display 200 may include a touchscreen. In particularembodiments, display 200 may present items in first region 410 andsecond region 430. First region 410 may include unread events 420.Unread events 420 are associated with events 170 that may have occurredafter user 112 ended the last authenticated session but prior to and/orup to the current authenticated session. A particular unread event 420may provide information about the particular event 170 with which theparticular unread event 420 is associated. Example information mayinclude the source of the particular transaction or communication, anamount of money (if any) associated with the particular transaction orcommunication, and/or a timestamp of the particular transaction orcommunication associated with the particular event 170. Display 200 mayalso include second region 430 which may present read events 430. Readevents 430 are associated with events 170 that may have occurred priorto user 112 ending the last authenticated session. Read events 430 mayprovide the same type of information provided by unread events 420.

Display 200 may also include a mechanism to allow user 112 to viewmultiple unread events 420 that may not all be displayed at the sametime in first region 410. For example, display 200 may include scrollbar 450. When user 112 interacts with scroll bar 450, display 200 mayscroll first region 410 to present additional unread events 420. Incertain embodiments, when display 200 has displayed all unread events420 in first region 410, first region 410 and second region 430 may bemerged together visually such that scroll bar 450 may scroll firstregion 410 in conjunction with second region 430 as if both regions werea single list.

Returning to FIG. 1, in operation, system 100 may provide a faster andmore convenient way for user 112 to manage and interact with informationassociated with accounts 140, transactions 150, financial services 160,and/or events 170. For example, device 114 may provide an interface touser 112 to allow user 112 to manage user preferences 165 for receivingand interacting with certain information. User 112 may choose particularaccounts 140, transactions 150, financial services 160, and/or events170 for which to receive certain information. The user preferences 165of user 112 may prioritize receiving information from one source overanother source. User 112 may choose to receive notifications for certainaccounts 140, transactions 150, financial services 160, and/or events170 while choosing not to receive notification for other accounts 140,transactions 150, financial services 160, and/or events 170. Once user112 has updated user preferences 165, device 114 may store userpreferences 165 in memory 134 and/or may communicate user preferences165 to server 110 via message 180 for storage in memory 134.

Device 114 may also provide up to date information to user 112 regardinga variety of financial services 160. This operation will be describedwith reference to FIG. 2. Device 114 may retrieve user preferences 165which notify device 114 of what particular information to display touser 112. In certain embodiments, user preferences 165 may notify device114 to present information associated with particular financial services160. For example, after determining which financial services 160 todisplay from user preferences 165, device 114 may communicate message180 to server 110 requesting information associated with particularfinancial services 160. In response, server 110 may communicate therequested information to device 114. Device 114 may then presentinformation associated with a first financial service 160 in firstregion 210, information associated with a second financial service 160in second region 220, information associated with a third financialservice 160 in third region 230, and information associated with afourth financial service 160 in fourth region 240.

Any one of the regions of display 200 is operable to present updates tothe information associated with a particular financial service 160. Forexample, server 110 may determine information associated with aparticular financial service 160 is out of date due to an occurrence ofan event such as a new bill, transaction, event, and/or any otheroccurrence suitable for a financial institution. Server 110 maycommunicate updated information via message 180 to device 114. Device114 may receive the updated information and may indicate the update touser 112 using a visual and/or audio cue. For example, device 114 maypresent a graphical counter in a particular region and an update to thefinancial service 160 may comprise incrementing the graphical counter.

After information has been presented to user 112 in the various regions,user 112 may select one of the financial services 160 for presentationof additional information. In certain embodiments, user 112 may touch aparticular region indicating the selection of the particular financialservice 160. In response to the selection by user 112, device 114 maycommunicate message 180 to server 110 requesting further informationassociated with the particular financial service 160. Server 110 mayretrieve information associated with the particular financial service160 from memory 134 which may include accessing information stored asaccounts 140, transactions 150, and/or events 170. Once the appropriateinformation is retrieved, device 114 may display the informationregarding financial service 160 on display 200. For example, display 200may replace information being displayed in first region 210, secondregion 220, third region 230, and fourth region 240 with informationassociated with the selected financial service 160. In certainembodiments, the selection of the particular financial service 160 mayreset to zero any graphical counters for unread messages that may havebeen associated with the financial service 160.

Device 114 may also provide the functionality for user 112 to review andmanage information associated with accounts 140, transactions 150,financial services 160, and/or events 170. For example, device 114 mayretrieve information associated with transactions 150 and/or events 170from memory 134. Device 114 may then present the information to user 112in first region 310 of display 200. In certain embodiments, device 114may display the first of many events 170 or transactions 150 based on atime associated with the item, whether the item has not been reviewed,whether the item has been marked for further review, or any other rulesuitable for a particular purpose.

Device 114 may also present second region 320 that provides user 112with the option to mark a particular transaction 150 or event 170 forfurther review. In certain embodiments, second region 320 may bepre-selected indicating that user 112 should review the particulartransaction 150 or event 170. Device 114 may also present third region330, which when selected, may indicate that user 112 has reviewed theparticular transaction 150 or event 170.

Device 114 may determine that in addition to the information for aparticular transaction 150 or event 170 that is being currentlydisplayed, there are additional transactions 150 or events 170 that maybe displayed. For example, device 114 may have a plurality oftransactions 150 or events 170 to display. Device 114 may display afirst one of the plurality of transactions 150 or events 170 in firstregion 310. Device 114 may display an indication of the rest of theplurality of transactions 150 or events 170, if any, in fourth regions360.

For any item presented in first region 310, user 112 may indicate thecurrent item should be marked for further review. User 112 may do thisby interacting with second region 320 indicating that the particulartransaction 150 or event 170 is marked for further review. In certainembodiments, in response to marking the particular transaction 150 orevent 170 for further review, message 180 may be communicated to server110 indicating that user 112 has marked the particular transaction 150or event 170 for further review. Server 110 may determine that thisindicates that user 112 is challenging the accuracy of transaction 150or event 170 and may initiate appropriate rules for handling customerdisputes.

User 112 may also indicate that the current item in first region 310 hasbeen reviewed. For example, user 112 may interact with third region 330indicating the current item has been reviewed. Additionally, user 112may swipe from the first region 312 to the fifth region 340 indicatingthat the next item should be displayed. In response to user 112indicating that the next item, if any, should be displayed, device 114may update first region 310, second region 320, and third region 330accordingly. For example, device 114 may display a transaction 150 orevent 170 that occurred subsequent to the previously displayedtransaction 150 or event 170 in first region 310. Fourth regions 360 mayalso be updated to display an appropriate number of transactions 150 orevents 170.

The operation of presenting user 112 with information about transactions150 and events 170 that occurred subsequent to the last session of user112 will now be described. Device 114 may authenticate user 112 aninitial time. Device 114 may determine when user 112 logs out from aparticular application or otherwise ceases to user a particularapplication that may provide the present operation ending the session ofuser 112. Device 114 may then detect a second authentication of user112. In response to detecting an authentication of user 112, device 114may then retrieve information about transactions 150 and/or events 170that may have occurred subsequent to the last session of user 112. Afterdetermining which transactions 150 and/or events 170 may have occurredsince the last session of user 112, device 114 may display theinformation associated with particular transactions 150 or events 170that occurred since the last session of user 112 in first region 410 ofdisplay 200 as unread events 420.

Device 114 may also determine if any transactions 150 and/or events 170occurred prior to the last session of user 112. Device 114 may displayinformation associated with particular transactions 150 and/or events170 as read events 440 in second region 430 of display 200.

In certain instances, unread events 420 may not all be displayed at thesame time in first region 410 due to space constraints of first region410. In such an instance, device 114 may present scroll bar 450 indisplay 200. Device 114 may detect a touch from user 112 on or nearscroll bar 450 indicating the desire of user 112 to view more unreadevents 420. In response to the interaction of user 112 with scroll bar450, device 114 may display more unread events 420 by scrolling firstregion 430 upward. When all unread events 420 have been displayed, firstregion 410 and second region 420 may be merged together visually suchthat scroll bar 450 may scroll first region 410 in conjunction withsecond region 430 as if both regions were a single list.

In particular embodiments, system 100 provides user 112 with anintuitive and fast interface through which to manage and reviewelectronic notices and transactions. In this manner, system 100 mayencourage and incentivize users 112 to overcome any fears or concernswith respect to using device 114 to manage and review electronic noticesand transactions. Furthermore, in particular embodiments, device 114 maybe a mobile device 114, which may require less processing power topresent an interface to user 112 than a workstation or a personalcomputer. Additionally, mobile device 114 may execute application 190 toinitiate the functions described above, which may generate less networktraffic than a workstation or a personal computer performing the sameoperations, thus improving network efficiency by reducing load.

FIG. 5 is a flowchart illustrating a method for managing electronicnotices. Mobile device 114 may perform the example method of FIG. 5. Inparticular embodiments, mobile device 114 may execute application 190that causes mobile device 114 to perform the example method of FIG. 5.At step 500, device 114 may provide an interface to user 112 to allowuser 112 to manage user preferences 165 for receiving and interactingwith certain information. User 112 may choose particular accounts 140,transactions 150, financial services 160, and/or events 170 for which toreceive certain information. The user preferences 165 of user 112 mayprioritize receiving information from one source over another source.User 112 may choose to receive notifications for certain accounts 140,transactions 150, financial services 160, and/or events 170 whilechoosing not to receive notification for other accounts 140,transactions 150, financial services 160, and/or events 170. Mobiledevice 114 may determine whether user 112 has updated user preference165. If user 112 has updated user preferences 165, the example methodmay proceed to step 510. Otherwise, the example method may proceed tostep 520. At step 510, once user 112 has updated user preferences 165,device 114 may store user preferences 165 in memory 134 and/or maycommunicate user preferences 165 to server 110 via message 180 forstorage in memory 134. The example method may then proceed to step 530.

At step 520, mobile device 114 may retrieve user preferences 165 whichnotify device 114 of what particular information to display to user 112.In certain embodiments, user preferences 165 may notify mobile device114 to present information associated with particular financial services160. For example, after determining which financial services 160 todisplay from user preferences 165, mobile device 114 may communicatemessage 180 to server 110 requesting information associated withparticular financial services 160. In response, server 110 maycommunicate the requested information to mobile device 114. At step 530,mobile device 114 may then present information associated with a firstfinancial service 160 in first region 210. At step 540, mobile device114 may present information associated with a second financial service160 in second region 220. At step 550, mobile device 114 may presentinformation associated with a third financial service 160 in thirdregion 230. At step 560, mobile device 114 may present informationassociated with a fourth financial service 160 in fourth region 240.

Any one of the regions of display 200 is operable to present updates tothe information associated with a particular financial service 160. Forexample, at step 570 server 110 may determine information associatedwith a particular financial service 160 is out of date due to anoccurrence of an event such as a new transaction 150, event 170, and/orany other occurrence suitable for a financial institution. If an updateis found, server 110 may communicate updated information via message 180to device 114 and the example method may proceed to step 580. Otherwise,the example method may proceed to step 585.

At step 580, mobile device 114 may receive the updated information andmay indicate the update to user 112 using a visual and/or audio cue. Forexample, device 114 may present a graphical counter in a particularregion and an update to the financial service 160 may compriseincrementing the graphical counter. The example method may then returnto step 570 to check for more updates.

After information has been presented to user 112 in the various regions,at step 585, user 112 may select one of the financial services 160 forpresentation of additional information. In certain embodiments, user 112may touch a particular region indicating the selection of the particularfinancial service 160. If no touch is detected, then the example methodmay end. If a touch is detected, the example method may proceed to step590. At step 590, in response to the selection by user 112, device 114may communicate message 180 to server 110 requesting further informationassociated with the particular financial service 160. Server 110 mayretrieve information associated with the particular financial service160 from memory 134 which may include accessing information stored asaccounts 140, transactions 150, and/or events 170. Once the appropriateinformation is retrieved, device 114 may display the informationregarding financial service 160 on display 200. For example, display mayreplace information being displayed in first region 210, second region220, third region 230, and fourth region 240 with information associatedwith the selected financial service 160. In certain embodiments, theselection of the particular financial service 160 may reset to zero anygraphical counters for unread messages that may have been associatedwith the financial service 160.

By performing the example method above, mobile device 114 may provideseveral technical advantages. For example, mobile device 114 may reducethe load on network 120. Furthermore, by executing application 190,mobile device 114 may reduce the amount of processing power needed toperform various functions related to the management and retrieval ofelectronic notices.

FIG. 6 is a flowchart illustrating a method for managing electronictransactions. Mobile device 114 may perform the example method of FIG.6. In particular embodiments, mobile device 114 may execute application190 that causes mobile device 114 to perform the example method of FIG.6. The example method of FIG. 6 begins at step 600 where mobile device114 may retrieve information associated with transactions 150 and/orevents 170 from memory 134. At step 610, mobile device 114 may thenpresent the information to user 112 in first region 310 of display 200.In certain embodiments, device 114 may display the first of many events170 or transactions 150 based on a time associated with the item,whether the item has not been reviewed, whether the item has been markedfor further review, or any other rule suitable for a particular purpose.

At step 620, mobile device 114 may present second region 320 thatprovides user 112 with the option to mark a particular transaction 150or event 170 for further review. In certain embodiments, second region320 may be pre-selected indicating that user 112 should review theparticular transaction 150 or event 170. At step 630, mobile device 114may present third region 330, which when selected, may indicate thatuser 112 has reviewed the particular transaction 150 or event 170.

At step 640, mobile device 114 may determine that in addition to theinformation for a particular transaction 150 or event 170 that is beingcurrently displayed, there are additional transactions 150 or events 170that may be displayed. Device 114 may display these one or moreadditional transactions 150 or events 170, if any, in fourth regions360.

For any item presented in first region 310, user 112 may indicate thecurrent item should be marked for further review. At step 650, mobiledevice may detect whether user 112 marked the current transaction 150 orevent 170 for further review. For example, user 112 may do this byinteracting with second region 320 indicating that the particulartransaction 150 or event 170 is marked for further review and theexample method may proceed to step 660. Otherwise, the example methodmay proceed to step 670. At step 660, in response to marking theparticular transaction 150 or event 170 for further review message 180may be communicated to server 110 indicating that user 112 has markedthe particular transaction 150 or event 170 for further review. Server110 may determine that this indicates that user 112 is challenging theaccuracy of transaction 150 or event 170 and may initiate appropriaterules for handling customer disputes. The example method may proceed tostep 670.

At step 670, mobile device 114 may determine whether the currenttransaction 150 or event 170 has been reviewed. For example, user 112may indicate that the current item in first region 310 has been reviewedby interacting with third region 330 indicating the current item hasbeen reviewed. Additionally, user 112 may swipe from the first region312 to the fifth region 340 indicating that the next items should bedisplayed. If user 112 has reviewed the current item, the example methodmay proceed to step 680. Otherwise, the example method may end.

At step 680, in response to user 112 indicating that the next item, ifany, should be displayed, mobile device 114 may update first region 310,second region 320, and third region 330 accordingly. For example, mobiledevice 114 may clear information regarding the current item from firstregion 310, second region 320, and third region 330 and proceed to step690. At step 690, mobile device 114 may determine whether a transaction150 or event 170 occurred subsequent to the previously displayedtransaction 150 or event 170 in first region 310. If there are otheritems to be displayed, the example method may return to step 610.Otherwise, the example method may end.

By performing the example method above, mobile device 114 may provideseveral technical advantages. For example, mobile device 114 may reducethe load on network 120. Furthermore, by executing application 190,mobile device 114 may reduce the amount of processing power needed toperform various functions related to the management and retrieval ofelectronic notices.

FIG. 7 is a flowchart illustrating a method for presenting electronicnotices. Mobile device 114 may perform the example method of FIG. 7. Inparticular embodiments, mobile device 114 may execute application 190that causes mobile device 114 to perform the example method of FIG. 7.At step 700, mobile device 114 may authenticate user 112 an initialtime. At step 705, mobile device 114 may determine when user 112 logsout from a particular application or otherwise ceases to use aparticular application that may provide the present operation ending thesession of user 112. At step 710, mobile device 114 may then detect asecond authentication of user 112. At step 715, in response to detectingan authentication of user 112, device 114 may then retrieve informationabout transactions 150 and/or events 170 that may have occurredsubsequent to the last session of user 112. At step 720, mobile device114 may determine whether any transactions 150 and/or events 170 haveoccurred subsequent to the last session of user 112. If mobile device114 determines that no transactions 150 or events 170 occurredsubsequent to the last session of user 112, then the example method mayproceed to step 745. Otherwise, the example method may proceed to step725. At step 725, after determining which transactions 150 and/or events170 may have occurred since the last session of user 112, device 114 maydisplay the information associated with particular transactions 150 orevents 170 that occurred since the last session of user 112 in firstregion 410 of display 200 as unread events 420. The example method mayproceed to step 730.

At step 730, mobile device 114 may determine if any transactions 150and/or events 170 occurred prior to the last session of user 112. Ifmobile device 114 determines that no transactions or events occurredprior to the last session of user 112, the example method may proceed tostep 740. Otherwise, the example method may continue to step 735 wheremobile device 114 may display information associated with particulartransactions 150 and/or events 170 as read events 440 in second region430 of display 200. The example method may proceed to step 740.

In certain instances unread events 420 may not all be displayed at thesame time in first region 410 due to space constraints of first region410. In such an instance, device 114 may present scroll bar 450 indisplay 200. At step 740, mobile device 114 may detect a touch from user112 on or near scroll bar 450 indicating the desire of user 112 to viewmore unread events 420. If no touch is detected, the example method mayend, otherwise, the example method may proceed to step 745. At step 745,in response to the interaction of user 112 with scroll bar 450, mobiledevice 114 may determine whether there are more transactions 150 orevents 170 that occurred after the last session of user 112. If thereare no other items fitting such a description, the example method mayproceed to step 755. Otherwise the example method may proceed to step750 where mobile device 114 may display more unread events 420 byscrolling first region 430 upward. At step 755, when all unread events420 have been displayed, first region 410 and second region 420 may bemerged together visually such that scroll bar 450 may scroll firstregion 410 in conjunction with second region 430 as if both regions werea single list.

By performing the example method above, mobile device 114 may provideseveral technical advantages. For example, mobile device 114 may reducethe load on network 120. Furthermore, by executing application 190,mobile device 114 may reduce the amount of processing power needed toperform various functions related to the management and retrieval ofelectronic notices.

Although the present disclosure includes several embodiments, a myriadof changes, variations, alterations, transformations, and modificationsmay be suggested to one skilled in the art, and it is intended that thepresent disclosure encompass such changes, variations, alterations,transformations, and modifications as fall within the scope of theappended claims.

What is claimed is:
 1. An apparatus comprising: a memory operable tostore user preferences associated with a user; and a processorcommunicatively coupled to the memory, the processor operable to:present, in a first region of a display, information associated with afirst service based at least in part upon the user preferences; present,in a second region of the display, information associated with a secondservice based at least in part upon the user preferences; present, in athird region of the display, information associated with a third servicebased at least in part upon the user preferences; present, in a fourthregion of the display, information associated with a fourth servicebased at least in part upon the user preferences; receive an update tothe information associated with the first service; present, in the firstregion of the display, the update to the information associated with thefirst service, wherein not all of the information associated with thefirst service is visible in the first region of the display due to spaceconstraints and at least one unread event is not visible in the firstregion; detect a first touch on the first region of the displayindicating a selection of the first service; in response to scrolling bythe user, determine that each one of the at least one unread events inthe first region have been presented to the user; and when each of theat least one unread events have been displayed in the first region ofthe display, merge the first region and the second region of the displaytogether visually to enable the user to scroll the first region inconjunction with the second region as a single list.
 2. The apparatus ofclaim 1, wherein the processor is further operable to receive anindication that the user has altered the user preferences.
 3. Theapparatus of claim 2, wherein the update to the information associatedwith the first service is received in response to receiving theindication.
 4. The apparatus of claim 1, wherein receiving an update tothe information associated with the first service comprises: receivingone or more messages associated with the first service; and determininga total number of unread received messages.
 5. The apparatus of claim 4,wherein presenting the update to the information associated with thefirst service comprises displaying the total number of unread receivedmessages in the first region of the display.
 6. The apparatus of claim5, wherein the processor is further operable to reset the total numberof unread received messages to zero in response to detecting the firsttouch.
 7. The apparatus of claim 1, wherein the processor is furtheroperable to: present, in a fifth region of the display, an option toview information associated with a plurality of events; detect a secondtouch on the fifth region of the display indicating a selection of theoption to view information associated with the plurality of events; andpresent, on the display, information associated with the plurality ofevents in response to detecting the second touch.
 8. A methodcomprising: storing user preferences associated with a user; presenting,in a first region of a display, information associated with a firstservice based at least in part upon the user preferences; presenting, ina second region of the display, information associated with a secondservice based at least in part upon the user preferences; presenting, ina third region of the display, information associated with a thirdservice based at least in part upon the user preferences; presenting, ina fourth region of the display, information associated with a fourthservice based at least in part upon the user preferences; receiving anupdate to the information associated with the first service; presenting,in the first region of the display, the update to the informationassociated with the first service, wherein not all of the informationassociated with the first service is visible in the first region of thedisplay due to space constraints and at least one unread event is notvisible in the first region; detecting a first touch on the first regionof the display indicating a selection of the first service; in responseto scrolling by the user, determining that each one of the at least oneunread events in the first region has been presented to the user; andwhen each of the at least one unread events have been displayed in thefirst region of the display, merging the first region and the secondregion of the display together visually to enable the user to scroll thefirst region in conjunction with the second region as a single list. 9.The method of claim 8, further comprising receiving an indication thatthe user has altered the user preferences.
 10. The method of claim 9,wherein the update to the information associated with the first serviceis received in response to receiving the indication.
 11. The method ofclaim 8, wherein receiving an update to the information associated withthe first service comprises: receiving one or more messages associatedwith the first service; and determining a total number of unreadreceived messages.
 12. The method of claim 11, wherein presenting theupdate to the information associated with the first service comprisesdisplaying the total number of unread received messages in the firstregion of the display.
 13. The method of claim 12, further comprisingresetting the total number of unread received messages to zero inresponse to detecting the first touch.
 14. The method of claim 8,further comprising: presenting, in a fifth region of the display, anoption to view information associated with a plurality of events;detecting a second touch on the fifth region of the display indicating aselection of the option to view information associated with theplurality of events; and presenting, on the display, informationassociated with the plurality of events in response to detecting thesecond touch.
 15. One or more non-transitory computer-readable mediacomprising logic, the logic when executed by one or more processorsoperable to perform operations comprising: storing user preferencesassociated with a user; presenting, in a first region of a display,information associated with a first service based at least in part uponthe user preferences; presenting, in a second region of the display,information associated with a second service based at least in part uponthe user preferences; presenting, in a third region of the display,information associated with a third service based at least in part uponthe user preferences; presenting, in a fourth region of the display,information associated with a fourth service based at least in part uponthe user preferences; receiving an update to the information associatedwith the first service; presenting, in the first region of the display,the update to the information associated with the first service, whereinnot all of the information associated with the first service is visiblein the first region of the display due to space constraints and at leastone unread event is not visible in the first region; detecting a firsttouch on the first region of the display indicating a selection of thefirst service; and in response to scrolling by the user, determiningthat each one of the at least one unread events in the first region havebeen presented to the user; and when each of the at least one unreadevents have been displayed in the first region of the display, mergingthe first region and the second region of the display together visuallyto enable the user to scroll the first region in conjunction with thesecond region as a single list.
 16. The media of claim 15, wherein thelogic is further operable to perform operations comprising receiving anindication that the user has altered the user preferences.
 17. The mediaof claim 16, wherein the update to the information associated with thefirst service is received in response to receiving the indication. 18.The media of claim 15, wherein receiving an update to the informationassociated with the first service comprises: receiving one or moremessages associated with the first service; and determining a totalnumber of unread received messages.
 19. The media of claim 18, whereinpresenting the update to the information associated with the firstservice comprises displaying the total number of unread receivedmessages in the first region of the display.
 20. The media of claim 19,wherein the logic is further operable to perform operations comprisingresetting the total number of unread received messages to zero inresponse to detecting the first touch.
 21. The media of claim 15,wherein the logic is further operable to perform operations comprising:presenting, in a fifth region of the display, an option to viewinformation associated with a plurality of events; detecting a secondtouch on the fifth region of the display indicating a selection of theoption to view information associated with the plurality of events; andpresenting, on the display, information associated with the plurality ofevents in response to detecting the second touch.